Query execution across multiple graphs

ABSTRACT

Examples of the present disclosure describe systems and methods for query execution across multiple graphs. In an example, a graph or isolated collection may be split into multiple subparts, such that each subpart may store information of the isolated collection. Cross-collection reference resources may be used to reference resources that are stored by other isolated collection subparts. A breadth-first search of an isolated collection subpart may be performed in order to identify matches or potential matches in an isolated collection subpart. In an example, a potential match may comprise a cross-collection reference resource, which may reference a resource in another isolated collection subpart. Once query execution has completed in the isolated collection subpart, query execution may be paused and transferred to another isolated collection subpart that comprises a resource referenced by a cross-collection resource reference. Accordingly, query execution may resume in the subsequent isolated collection subpart.

BACKGROUND

Graphs or isolated collections may be used to store a wide variety ofinformation. Typically, such storage structures may be retained inoperating memory in order to facilitate improved access, query, andstorage times. However, as the amount of stored information increases,it may become difficult to retain all of the information in memory. Thisissue may be resolved by splitting the graph into multiple sub-graphsacross multiple computing devices.

It is with respect to these and other general considerations that theaspects disclosed herein have been made. Also, although relativelyspecific problems may be discussed, it should be understood that theexamples should not be limited to solving the specific problemsidentified in the background or elsewhere in this disclosure.

SUMMARY

Examples of the present disclosure describe systems and methods forquery execution across multiple graphs. In an example, a graph orisolated collection may be split into multiple subparts, such that eachsubpart may store information of the isolated collection. Across-collection or cross-graph reference resource may be used in anisolated collection subpart to reference a resource stored by anotherisolated collection subpart. As a result, an isolated collection havingmultiple subparts may be traversed by following the cross-collectionreference resources to access other subparts of the isolated collection.

When querying an isolated collection having multiple subparts, it may bedifficult to efficiently access multiple subparts containing informationassociated with the query. Accordingly, aspects of the presentdisclosure relate to performing a breadth-first search in an isolatedcollection subpart in order to identify matches or potential matches. Inan example, a potential match may comprise a cross-collection orcross-graph reference resource, which may reference a resource inanother isolated collection subpart. Once query execution has completedin an isolated collection subpart, query execution may be paused andtransferred to another isolated collection subpart that comprises aresource referenced by a cross-collection resource reference. Queryexecution may resume in the subsequent isolated collection subpart.Query execution may continually be transferred until query execution hascompleted.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Additionalaspects, features, and/or advantages of examples will be set forth inpart in the description which follows and, in part, will be apparentfrom the description, or may be learned by practice of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive examples are described with reference tothe following figures.

FIG. 1 illustrates an overview of an example system for query executionacross multiple isolated collection subparts.

FIGS. 2A and 2B illustrate overviews of example isolated collectionsubparts of an isolated collection across which queries may be executed.

FIG. 3 illustrates an overview of an example method for query executionacross multiple isolated collection subparts.

FIG. 4 illustrates an overview of an example method for executing across-collection query in an isolated collection subpart.

FIG. 5 is a block diagram illustrating example physical components of acomputing device with which aspects of the disclosure may be practiced.

FIGS. 6A and 6B are simplified block diagrams of a mobile computingdevice with which aspects of the present disclosure may be practiced.

FIG. 7 is a simplified block diagram of a distributed computing systemin which aspects of the present disclosure may be practiced.

FIG. 8 illustrates a tablet computing device for executing one or moreaspects of the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully below withreference to the accompanying drawings, which form a part hereof, andwhich show specific example aspects. However, different aspects of thedisclosure may be implemented in many different forms and should not beconstrued as limited to the aspects set forth herein; rather, theseaspects are provided so that this disclosure will be thorough andcomplete, and will fully convey the scope of the aspects to thoseskilled in the art. Aspects may be practiced as methods, systems ordevices. Accordingly, aspects may take the form of a hardwareimplementation, an entirely software implementation or an implementationcombining software and hardware aspects. The following detaileddescription is, therefore, not to be taken in a limiting sense.

The present disclosure provides systems and methods for query executionacross multiple graphs. In an example, a graph or isolated collectionmay be provided or stored using multiple subparts, such that informationof the isolated collection may be split across the subparts. Informationstored by the isolated collection may be represented using one or moreresources and relationships. In order to retrieve information from theisolated collection, a query comprising one or more parameters may beexecuted to identify target information relating to the one or moreparameters within the isolated collection. Unlike relational databases,queries within an isolated collection rely on identifying relationshipsbetween resources and examining properties of resources and/orrelationships within the isolated collection. Accordingly, a querywithin a graph may be executed by traversing the graph using one or more“anchor” resources. However, if an isolated collection is split intomultiple subparts, not all relevant resources and relationships may bepresent in the isolated collection subpart in which the query wasinitially executed. As such, a query for target data stored by theisolated collection may be performed by accessing information in one ormore subparts of the isolated collection in order to identify targetdata associated with the query.

In some examples, a graph or isolated collection may be comprised ofresources and relationships. A resource may be identified by a resourceidentifier, which may be a durable Uniform Resource Identifier (URI)pointing to the particular resource. The resource identifier may also bea uniform resource locator (URL), uniform resource name (URN), or othersuitable identifier or pointers pointing to the resource itself. In oneexample, the resource may be stored within an isolated collection. Inanother example, the resource may be stored in a data collection, whilean associated resource identifier may be stored in an isolatedcollection. For example, the resource may reside on a remote server, andthe resource identifier may be used to retrieve the resource (e.g., theresource may be stored on a remote web server, where the resourceidentifier comprises a URL). Identifying the location of a resource mayinclude parsing the resource identifier using, for example, regularexpressions, providing one or more portions of the resource identifierto a search utility, executing the resource identifier, etc.Relationships within the isolated collection may identify a correlationbetween two or more resources in the isolated collection. In someexamples, an isolated collection may be a unified dimensional model(UDM), a graph, or other collection of resources and relationships.

A property may be associated with or stored by a resource orrelationship of an isolated collection. In an example, the property maybe comprised of a name and a value, such that the property may be usedto store information relating to a resource or relationship. As anexample, an “email” property (e.g., having the name “email”) for a“person” resource may store an email address (e.g., as the value for the“email” property) for the person to which the “person” resource relates.In another example, a “relation” resource for a “family member”relationship may indicate that the “family member” relationshipspecifies a “brother” relationship for the relationship indicated by the“family member” relationship. As will be appreciated, a property maycontain information other than a name and/or a value and may be storedas or associated with any type of information within a graph or anisolated collection.

An isolated collection may be queried to identify or retrieve targetinformation (e.g., properties, resources, and/or relationships). Thequery may be comprised of one or more parameters or constraints relatingto a relationship type, the type or content of a resource, or any otherproperty of a relationship or a resource. In some examples, theparameters may relate to a plurality of resources (e.g., such as afriend-of-a-friend relationship or a resource that is common to aplurality of otherwise unrelated resources, etc.). The parameters of thequery may relate to one or more “anchor” resources or resource types,which may be used when executing a query to identify a context orstarting resource for query evaluation. As an example, an anchorresource may be a resource type or a plurality of resource typesassociated with a relationship, such that resources within the isolatedcollection matching the one or more resource types are identified andfurther evaluated based on the parameters of the query.

An isolated collection may be split into a plurality of subparts for anyof a variety of reasons, including, but not limited to, due to computingresource constraints, to comply with security guidelines, or for ease ofdata management. In some examples, the isolated collection may be splitsuch that similar types or domains of information may reside in similarsubparts of the isolated collection. In other examples, the isolatedcollection may be split in order to minimize or reduce cross-collectionquerying. As an example, a subpart of an isolated collection maycomprise information relating to a similar topic or information that isoften accessed together, thereby increasing the likelihood that a queryfor information that is related to the topic may be executed withoutaccessing information from another isolated collection subpart. It willbe appreciated that an isolated collection may be split for any of avariety of reasons or may be split randomly, among other techniques.Further, content of isolated collection subparts need not be mutuallyexclusive, such that a resource or relationship may exist in a pluralityof isolated collection subparts.

An isolated collection having multiple subparts may comprise one or morecross-collection or cross-graph reference resources, which may provide areference to one or more resources in another isolated collectionsubpart. Accordingly, a cross-collection reference resource may indicatethat additional information relating to a resource or relationship isavailable in another subpart of an isolated collection. Thecross-collection reference resource may comprise a resource identifierof a resource to which it refers, a query that may be used to identify aresource, or an identifier associated with an isolated collectionsubpart that contains a referenced resource, among other descriptors. Insome examples, the cross-collection reference resource may compriseadditional information, such as cached information or one or moreproperties associated with a referenced resource, among otherinformation.

A query for information in an isolated collection may be compiled orotherwise processed in order to generate a query that may be executed inthe isolated collection. In some examples, compiling a query maycomprise performing one or more optimizations (e.g., based on the orderof parameters, the topology specified by the query, etc.). The resultingquery may be a byte code program, a file (e.g., an XML or JSON file,etc.), or other distributable, such that the compiled query may beprovided to any of a variety of computing devices or processors forexecution or evaluation. In some examples, a virtual machine may be usedto execute the query. While example query compilation and executionstrategies are discussed herein, it will be appreciated that a query maybe processed using other techniques without departing from the spirit ofthis disclosure.

When executing a query, an initial isolated collection subpart may bedetermined in which the query may be initially executed. Thedetermination may be based on an analysis of one or more parameters ofthe query, such that it may be determined that an isolated collectionsubpart may have resources or relationships that are more related to thequery than other isolated collection subparts. As an example, it may bedetermined that a query is related to people resources, so an isolatedcollection subpart having predominantly people resources may be a betterinitial isolated collection subpart than an isolated collection subparthaving few people resources. The determination may be based on otherinformation, such as the topology of a subpart (e.g., its structure, thenumber of relationships among resources, the number of resources of agiven type, etc.) or the uniqueness or frequency of information withinthe subpart (e.g., the frequency of properties, resources, and/orrelationships). The initial isolated collection subpart may be selectedso as to minimize or reduce the amount of external information (e.g.,stored by other isolated collection subparts, stored by other computingdevices, etc.) that may be required when executing the query.

Executing the query may comprise generating, storing, or accessingexecution context information, including, but not limited to, atraversal path data structure, a data storage structure, or a securitycontext. In an example, the traversal path data structure may compriseinformation associated with resources and relationships that have beentraversed while executing the query, such as resources and/orrelationships that are positive matches, potential matches, and/ornegative matches. Potential matches may be identified based ondetermining that information in the isolated collection subpart matchesthe query, but additional relevant information (e.g., as may beindicated by a cross-collection reference resource) is available in oneor more other isolated collection subparts, thereby requiring furtheranalysis based on information external to the isolated collectionsubpart.

A data storage structure may be used to store data from one or moreisolated collection subparts that is relevant to the query execution. Asan example, if a query parameter indicates that a match of the querycomprises a resource having a property with a certain value, propertyvalues for matching or potentially matching resources in an isolatedcollection subpart may be stored in the data storage structure, suchthat they may be evaluated based on information in subsequent isolatedcollection subparts. Similarly, if a query indicates that results shouldbe filtered after matches are identified, information relevant tofiltering the matches may be stored by the data storage structure. As aresult, information from one or more isolated collection subpartsrelating to query execution may be stored for later evaluation, suchthat at least a part of the information need not be later accessed fromisolated collection subparts that have already be evaluated as part ofthe query execution. In some examples, a query execution occurring in asingle isolated collection subpart may be performed without a datastorage structure, as the relevant information for executing the querymay already be available based on the content of the isolated collectionsubpart in which the query is executing.

A security context may be used to limit access to resources orrelationships in the isolated collection that may be access-restrictedfrom the requestor. The security context may comprise credentials,security claims, access rules, or one or more groups associated with therequestor, among other security information. As a result, the securitycontext may be evaluated when executing the query in one or moreisolated collection subparts, thereby ensuring that the target datareturned to the requestor conforms to the access restrictions specifiedby the security context.

While examples of execution context information are discussed herein, itwill be appreciated that additional or alternative execution contextinformation may be generated, stored, or accessed when executing aquery. In an example, execution context information may comprise any ofa variety of information that may be useful when executing the query. Insome examples, the execution context information may serve as a cache,thereby reducing the need to issue separate or additional accessrequests for information that may have already been accessed, requested,or available while executing a query. In other examples, executioncontext information may be pruned or otherwise managed while executing aquery, such that information that is no longer needed or relevant may beremoved or omitted. As an example, a data storage structure may bepruned to remove information associated with resources or relationshipsthat were previously potential matches but have since been eliminated.Similarly, a traversal path data structure may be pruned to omitpotential matches that have been eliminated. As a result, the executioncontext information may be managed so as to minimize or reduce theamount of information that is passed between isolated collectionsubparts.

After executing a query in an initial isolated collection subpart, itmay be determined that query execution should continue in one or moresubsequent isolated collection subparts. The determination may be basedon identifying one or more cross-collection reference resources in theset of matches or potential matches. Accordingly, query execution may bepaused and the query (e.g., the compiled query and at least part of theexecution context information, etc.) may be transmitted for execution ina subsequent isolated collection subpart. The subsequent isolatedcollection subpart may be identified using a similar technique as wasused to identify the initial isolated collection subpart, wherein thesubsequent isolated collection subpart may be determined to contain ormay be determined to be likely to contain information associated withthe query. In an example, this may comprise evaluating one or more ofthe cross-collection reference resources. Query execution may then beresumed in the subsequent isolated collection subpart.

Eventually, the query execution may complete. This may comprisedetermining that no further cross-collection reference resources havebeen identified or that there are no additional resources andrelationships to evaluate that are relevant to the query, among otherconditions. As a result, the execution context information may be usedto generate a response comprising the target data. In an example, atraversal path data structure comprising resources and/or relationshipsthat were identified as a match or a potential match for the query maybe evaluated. The evaluation may comprise evaluating information storedin a data storage structure of the execution context information, suchthat information associated with the relevant resources and/orrelationships of the traversal path data structure may be used togenerate and return the identified target data.

FIG. 1 illustrates an overview of an example system 100 for queryexecution across multiple isolated collection subparts. System 100comprises client devices 102-106, which communicate with storage system108. In an example, each of client devices 102-106 may be a computingdevice, such as a mobile computing device, a table computing device, apersonal computing device, or any other type of computing device, or anycombination thereof. Client devices 102-106 may communicate with storagesystem 108 by way of a network, including, but not limited to, a localarea network, a wide area network, or the Internet. Storage system 108may be provided by one or more computing devices and, in some examples,may be a distributed storage system.

Storage system 108 comprises query compilation processor 110 and queryexecution manager 112. Query compilation processor 110 may receivequeries for information stored by storage system 108 and compile thereceived queries. In some examples, compiling a query may compriseperforming one or more optimizations according to aspects disclosedherein. As discussed above, a query may be compiled into a byte codeprogram, a file, or other distributable, such that the compiled querymay be provided to any of a variety of computing devices or processorsfor execution or evaluation. In an example, a virtual machine may beused to execute a compiled query. Query execution manager 112 may managethe execution of a compiled query, as may have been generated by querycompilation processor 110. Query execution manager 112 may manage theexecution of a query across an isolated collection comprising isolatedcollection subparts 114A-C.

In some examples, isolated collection subparts 114A-C may be stored orprovided by multiple computing devices. While discrete elements arediscussed herein with respect to FIG. 1, it will be appreciated thatfunctions described with respect to a specific element of system 100 maybe performed by other elements. As an example, one or more of isolatedcollection subparts 114A-C may comprise a query execution manager and/ora query compilation processor, rather than being directed by a singlequery execution manager 112 as illustrated in FIG. 1. Additionally,while three isolated collection subparts are shown in FIG. 1, it will beappreciated that aspects disclosed herein may be practiced with anisolated collection having any number of subparts.

Query compilation processor 110 may receive a query from one of clientdevices 102-106. In some examples, the query may be formulated using aquery language (e.g., Cypher Query Language, SPARQL, etc.) to accessinformation stored by isolated collection subparts 114A-C. Querycompilation processor 110 may compile the query according to aspectsdisclosed herein and provide the query to query execution manager 112.Query execution manager 112 may evaluate the query to identify whetherone of isolated collection subparts 114A-C would be a suitable initialisolated collection subpart in which to begin query execution. Theevaluation may comprise evaluating information associated with one ormore parameters of the query (e.g., resource types, relationship types,property types, topology information, uniqueness information, etc.). Insome examples, multiple isolated collection subparts 114A-C may becandidates for beginning query execution. As a result, query executionmanager 112 may identify an initial isolated collection subpart based onutilization information, proximity information (e.g., which isolatedcollection subpart is closest to the requestor and may therefore exhibitless latency, etc.), among other considerations. In some examples, queryexecution manager 112 may apply other logic or may randomly select anisolated collection subpart in which to begin execution.

Assuming, for the purpose of illustration, that query execution beginsin isolated collection subpart 114A, query execution may begin from oneor more anchor resources within the subpart. Accordingly, resources andrelationships associated with an anchor resource may be evaluated basedon parameters of the query, such that a positive match or potentialmatch may be identified. In some examples, a negative match may also bedetermined. Execution context information may be updated, such that atraversal path data structure may include positive matches, potentialmatches, and/or negative matches. In an example, isolated collectionsubpart 114A may comprise the relevant resources and relationships forquery execution, thereby enabling query execution to complete inisolated collection subpart 114A. As a result, target data comprisingresources and/or relationships matching the query may be provided toquery execution manager 112, which query execution manager 112 may thenprovide in response to the requestor.

In another example, resources and relationships that are relevant to thequery may exist outside of isolated collection 114A, and may be storedby isolated collection 114B and/or 114C. As a result, one or morecross-collection reference resources may be identified during theexecution of the query in isolated collection 114A. Execution contextinformation may be updated accordingly, such that a traversal path datastructure may indicate a potential match comprising a path between ananchor resource and a cross-collection reference resource. As discussedabove, a cross-collection reference resource may be a reference to oneor more resources stored in another isolated collection subpart. In someexamples, a data storage structure of the execution context informationmay be updated to store information associated with one or moreresources or relationships in isolated collection subpart 114A for laterreference. Executing the query in isolated collection 114A may compriseperforming a breadth-first search, wherein matches and potential matchesare identified in isolated collection subpart 114A, including anyrelevant cross-collection reference resources, before continuing thequery in a subsequent isolated collection subpart.

Once query execution completes (e.g., progresses until no more relevantresources and relationships may remain for evaluation), query executionmay be paused and transferred, such that the query and the executioncontext information may be executed in a subsequent isolated collectionsubpart. As illustrated, query execution manager 112 may pause the queryexecution, transfer the query to a subsequent isolated collectionsubpart, and use the execution context information to resume executionof the query in the subsequent isolated collection subpart. In anotherexample, isolated collection subpart 114A may manage execution of thequery and may provide the query and execution context information to asubsequent isolated collection subpart for continued execution. In someexamples, identifying the subsequent isolated collection subpart maycomprise evaluating a traversal path data structure in order to identifyone or more cross-collection resource references, which may be used toidentify one or more isolated collection subparts containing resourcesto which they refer. Query execution may then be continued in thesubsequent isolated collection subpart (e.g., isolated collectionsubpart 114B or 114C) according to aspects disclosed herein. Executionmay then either complete (e.g., if cross-collection reference resourcesare not identified when continuing the query execution, if no resourcesremain, etc.) or may again progress to another isolated collectionsubpart.

FIGS. 2A and 2B illustrate overviews of example isolated collectionsubparts 200 and 220 of an isolated collection across which queries maybe executed. As illustrated, isolated collection subpart 200 comprisesresources and relationships associated with calendaring information,while isolated collection subpart 220 comprises resources andrelationships associated with people in an organizational structure.While example domains are discussed with respect to isolated collectionsubparts 200 and 220, it will be appreciated that an isolated collectionmay be split based on any of a variety of criteria, associations, orlogic according to aspects disclosed herein.

With respect to isolated collection subpart 200 in FIG. 2A, MeetingA 208and MeetingB 212 are shown, wherein MeetingA 208 occurs at DateTimeA210, while MeetingB 212 occurs at DateTimeB 214. Resources 208-214 areillustrated using solid lines, indicating that information associatedwith resources 208-214 (e.g., properties, metadata, etc.) is stored inisolated collection subpart 200. PersonA 202 and PersonB 204 areillustrated as being related to MeetingA 208, thereby indicating thatthey are attendees of MeetingA 208. Similarly, PersonB 204 and PersonC206 are illustrated as being related to MeetingB 212, thereby indicatingthat they are attendees of MeetingB 212. Person resources 202-206 areillustrated using dashed lines to indicate that they arecross-collection reference resources, such that additional informationassociated with person resources 202-206 may be stored by anotherisolated collection subpart (e.g., isolated collection subpart 220 inFIG. 2B).

As discussed above, as cross-collection reference resources, personresources 202-206 may comprise information that may be used to identifyone or more resources to which the resources refer, including, but notlimited to, a resource identifier of a resource to which it refers, aquery that may be used to identify a resource, or an identifierassociated with an isolated collection subpart that contains areferenced resource, among other descriptors. In some examples, across-collection reference resource may comprise additional information,such as cached information or one or more properties associated with areferenced resource, among other information.

Turning now to isolated collection subpart 220 in FIG. 2B, isolatedcollection subpart 220 comprises person resources 222-226, which may bepart of an organizational hierarchy. As illustrated, PersonA 222 andPersonC 226 are managed by PersonB 224. Further, PersonA 222 and PersonB224 are associated with ProjectA 228, while PersonB 224 and PersonC 226are associated with ProjectB 230. Person resources 222-226 areillustrated using solid lines, indicating that isolated collectionsubpart 220 may store information associated with person resources222-226, such as properties or metadata, among other information.Project resources 228-230, however, are illustrated using dashed lines,thereby indicating that they are cross-collection reference resourcesreferring to project resources in another isolated collection subpart(not pictured).

In an example, isolated collection subparts 200 and 220 may be queriedaccording to aspects disclosed herein. A query may indicate that a matchis comprised of a meeting resource having an identifier of “MeetingA”that is associated with a datetime resource, in order to determine whenMeetingA is occurring. The query may be compiled according to aspectsdisclosed herein, such that it may be executed in one or more ofisolated collection subparts 200 and 220. It may be determined that thequery should be executed in isolated collection 200, as a result ofdetermining that isolated collection subpart 200 comprises meetingresources, while isolated collection subpart 220 does not. Accordingly,the query may use MeetingA 208 as an anchor resource and evaluate itsassociated resources and relationships. Upon identifying DateTimeA 210as an associated resource satisfying the query, query execution maycomplete, such that information associated with DateTimeA 210 may bereturned in response to the query.

In another example, a query may be provided in order to determine themanger associated with MeetingB 212. As such, the query may indicatethat a match is comprised of a meeting resource having an identifier of“MeetingB,” that is associated a person resource (e.g., the manager),wherein the person resource is further associated with another personresource (e.g., the subordinate) that was also an attendee of MeetingB.Isolated collection subpart 200 may again be selected as the initialisolated collection subpart for query execution, given that the anchorresource is a meeting resource and isolated collection subpart 220 doesnot have any meeting resources. Query execution may begin at MeetingB212, where associated resources and relationships may be identified.PersonB 204 and PersonC 206 may be identified as potential matches, as aresult of being person resources associated with MeetingB 212. However,due to identifying cross-collection reference resources, query executionmay be paused in order to transfer execution to another isolatedcollection subpart. Execution context information may be transferred aswell, according to aspects disclosed herein. In an example, theexecution context information may comprise a traversal path datastructure, indicating the potential matches comprising the paths betweenMeetingB 212 and PersonB 204, and MeetingB 212 and PersonC 206. Inanother example, the execution context information may comprise a datastorage structure having information associated with the resources andrelationships of the traversal path data structure. As an example, thedata storage structure may indicate that both PersonB 204 and PersonC206 are attendees of MeetingB 212, such that the information may laterbe referenced in order to determine whether a subordinate personidentified as being related to a manager person was also an attendee ofMeetingB.

The query may be transferred to isolated collection subpart 220, basedon information contained in the cross-collection reference resources. Inan example, PersonB 204 may indicate it refers to a person resourcehaving an identifier of “PersonB” in isolated collection subpart 220,while PersonC 206 may indicate it refers to a person resource having anidentifier of “PersonC” in isolated collection subpart 220. As a result,query execution may resume in isolated collection 220, wherein theanchor resources for the resumed query execution are the resourcesreferenced by PersonB 204 and PersonC 206: PersonB 224 and PersonC 226,respectively. When query execution resumes in isolated collectionsubpart 220, each of PersonB 224 and PersonC 226 may be evaluated todetermine whether any resources and relationships satisfy the query.Resuming at PersonC 226, it may be determined that PersonC 226 is notrelated to any subsequent person resources (as the arrow between PersonB224 and PersonC 226 is directional, indicating that PersonB 224 managesPersonC 226, rather than the other way around). Accordingly, PersonC 226cannot be a manager and the potential match comprising the path fromMeetingB 212 to PersonC 206 may be removed from the traversal path datastructure in the execution context information. However, given thatPersonC 206 was an attendee of MeetingB 212, information associated withPersonC 206 may remain in the data storage structure of the executioncontext information (e.g., indicating that PersonC 206 was an attendeeof MeetingB 212).

When the query is evaluated using PersonB 224 as the anchor resource, itmay be determined that PersonB 224 is associated with two people:PersonA 222 and PersonC 226. With respect to PersonA 222, it may bedetermined, based on the data storage structure of the execution contextinformation, that PersonA 222 was not an attendee of MeetingB 212. Thisdetermination may be made without further reference to isolatedcollection subpart 200, as a result of the information stored by thedata storage structure. When query execution moves to evaluate PersonC226, it may be determined that PersonC 226 was an attendee of MeetingB212, because PersonC 206 in isolated collection 200 (which is related toMeetingB 212 in isolated collection subpart 200) refers to PersonC 226.Accordingly, query execution may complete, such that target data may beprovided comprising the resources and relationships associated with thetraversal path between MeetingB 212, PersonB 224 (via PersonB 204), andPersonC 226.

FIG. 3 illustrates an overview of an example method 300 for queryexecution across multiple isolated collection subparts. Method 300 maybe performed by a storage system, such as storage system 108 in FIG. 1.In an example, method 300 may be performed by a computer device or aquery execution manager, among other devices or processors. Method 300begins at operation 302, where a query for data in an isolatedcollection may be received. The query may be received from a client,such as one of clients 102-106 in FIG. 1. In some examples, the querymay be formulated using a query language. As described above, the querymay be comprised of one or more parameters, which may be used toidentify target data stored by the isolated collection. In an example,the isolated collection may be comprised of a plurality of isolatedcollection subparts according to aspects disclosed herein.

At operation 304, an initial isolated collection subpart may beidentified for query execution. Identifying the initial isolatedcollection subpart may comprise evaluating one or more parameters of thequery and information relating to the plurality of isolated collectionsubparts. As an example, the query may be determined to relate to one ormore resource types. As a result, the initial isolated collectionsubpart may be selected based on the presence and/or frequency withwhich the resource type occurs in the isolated collection subpart. Inanother example, uniqueness or topology information may be evaluated,such that an isolated collection having more unique resources (e.g., ascompared to the resources of other isolated collection subparts)relating to the query may be selected as the initial isolated collectionsubpart. It will be appreciated that other techniques may be used toselect the initial isolated collection subpart without departing fromthe spirit of this disclosure.

Moving to operation 306, the query may be executed in the initialisolated collection subpart. In some examples, query execution maycomprise performing one or more steps of method 400 as discussed belowwith respect to FIG. 4. Executing the query may comprise evaluatingresources and relationships associated with one or more anchor nodes inorder to identify matching or potentially matching traversal paths,according to aspects disclosed herein. In an example, the query may becompiled or otherwise processed according to aspects disclosed herein.As described above, the query execution may comprise a breadth-firstsearch, wherein matches and potential matches are identified within theinitial isolated collection subpart before, if necessary, continuing theexecution in another isolated collection subpart. In some examples, theexecution may comprise generating or updating execution contextinformation, which may comprise a traversal path data structure and/or adata storage structure. The traversal path data structure may compriseinformation associated with positive matches, potential matches, and/ornegative matches that have been identified during query execution. Thedata storage structure may be used to store information associated withone or more evaluated resources and/or relationships that may beevaluated later based on information stored by other isolated collectionsubparts. As a result, additional information may not be required fromisolated collection subparts that have already been queried.

Eventually, query execution may reach a point at which further resourcesand relationships relating to the query are not available in theisolated collection subpart. Accordingly, flow progresses todetermination 308, where it may be determined whether query executionshould continue in another isolated collection subpart. Thedetermination may comprise an evaluation of the traversal path datastructure. In some examples, the determination may comprise evaluatingwhether any cross-collection reference resources are present in thetraversal path data structure. In other examples, the determination maycomprise determining whether there are any potential matches in thetraversal path (e.g., as opposed to just positive or negative matches).As an example, a potential match may indicate that additionalinformation may be needed to complete the evaluation of the match anddetermine whether the traversal path satisfies the query.

If it is determined that the query should not continue, flow branches“NO” to operation 310, where query execution results may be provided.Providing the query execution results may comprise generating anisolated collection comprising resources and relationships associatedwith the matching information or providing resource identifiersassociated with the matching information, among other representations.In an example, the execution context information may be used to filteror otherwise revise the results prior to providing them. Informationfrom a data storage structure may be used to evaluate matches that wereidentified in order to evaluate properties or other informationassociated with the identified matches. Flow terminates at operation310.

If, however, it is determined that query execution should continue inanother isolated collection subpart, flow branches “YES” to operation312, where query execution may be transferred to a subsequent isolatedcollection subpart. The subsequent isolated collection subpart may beidentified according to aspects disclosed herein. As an example, thesubsequent isolated collection subpart may be selected based ondetermining which isolated collection subpart is most referenced by oneor more cross-collection reference resources that were identified whenperforming the initial query execution. It will be appreciated thatother subpart selection techniques may be used. Transferring the querymay comprise transferring a distributable that was generated whencompiling the query (e.g., byte code, a JSON file, etc.) and/or at leasta part of an execution context associated with the query execution.

Moving to operation 314, query execution may continue in the subsequentisolated collection subpart. Query execution may continue in a similarmanner as was described above with respect to operation 306, however thequery may resume at one or more resources that were referenced by one ormore cross-collection reference resources from the initial isolatedcollection subpart. In some examples, execution context information maybe updated while executing the query, such that potential matches thatare eliminated may be pruned or revised from a traversal path datastructure and/or a data storage structure.

Flow then returns to determination 308, where it may again be determinedwhether query execution should continue in another isolated collectionsubpart. Flow may loop between operations 308, 312, and 314 while thereare other isolated collection subparts having information associatedwith the query (e.g., as may be determined by one or morecross-collection reference resources). Eventually, it may be determinedthat query execution has completed and should not continue in anotherisolated collection subpart, causing flow to progress to operation 310,where query execution results may be provided as discussed above. Flowterminates at operation 310.

FIG. 4 illustrates an overview of an example method 400 for executing across-collection query in an isolated collection subpart. In someexamples, query execution may comprise performing one or more steps ofmethod 400 as discussed below with respect to FIG. 4. Method 400 may beperformed by a storage system, such as storage system 108 in FIG. 1. Inan example, method 400 may be performed by a computer device or a queryexecution manager, among other devices or processors. Method 400 beginsat operation 402, where a query for execution in an isolated collectionsubpart may be received. In an example, the query may comprise one ormore parameters and/or may indicate an anchor resource. The query may bea compiled or otherwise distributable query as described herein. In someexamples, the query may be received along with execution contextinformation. In some examples, the query may be received from a queryexecution manager, a client, or from within a storage system (e.g., acomputing device storing another subpart of the isolated collection).

At operation 404, a resource or relationship may be identified that isassociated with an anchor resource of the query. The anchor resource maybe identified based on a unique identifier or one or more properties orrelationships, among other techniques. Moving to determination 406, itmay be determined whether the resource or relationship satisfies one ormore parameters of the query. The determination may comprise evaluatingone or more properties of the resource or relationship, evaluatingmetadata, or evaluating other information associated with the resourceor relationship. If it is determined that the resource or relationshipdoes not satisfy the query, flow branches “NO” to operation 404, whereanother resource or relationship may be identified. Flow may then loopbetween operations 404 and 406 until a resource or relationship thatsatisfies the query is identified.

If, however, it is determined at determination 406 that the resource orrelationship satisfies the query, flow branches “YES” to operation 408,where the isolated collection subpart may be traversed based on theevaluation. Continuing the traversal may comprise continuing to evaluateresources and relationships associated with the identified resource orrelationship to determine whether any subsequent resources orrelationships satisfy the query. If a subsequent resource orrelationship satisfies the query, the traversal path may be extendedaccordingly. At determination 410, it may be determined whether across-collection reference resource is part of the traversal path. If itis determined that a cross-collection reference resource is not part ofthe traversal path, flow branches “NO” to operation 408, where thetraversal may continue, again identifying resources or relationshipsthat satisfy the query to extend the traversal path.

If, however, it is determined that a cross-collection reference resourceis part of the traversal path, flow branches “YES” to operation 412,where the traversal path may be stored as part of execution contextinformation, which may later be referenced when continuing the queryexecution in another isolated collection subpart. As a result ofidentifying a cross-collection reference resource as part of thetraversal path, the traversal path may end with the cross-collectionreference resource, such that the traversal may continue to identifyother potential or positive matches within the isolated collectionsubpart, thereby returning to operation 404. Flow may continue betweenoperations 404-412 until it has been determined that there are nofurther relevant resources for evaluation in the isolated collectionsubpart. In some examples, query execution may then be paused, the queryand the execution context information may be transferred to anotherisolated collection subpart, and execution may resume in the otherisolated collection subpart according to aspects disclosed herein.

FIGS. 5-8 and the associated descriptions provide a discussion of avariety of operating environments in which aspects of the disclosure maybe practiced. However, the devices and systems illustrated and discussedwith respect to FIGS. 5-8 are for purposes of example and illustrationand are not limiting of a vast number of computing device configurationsthat may be utilized for practicing aspects of the disclosure, describedherein.

FIG. 5 is a block diagram illustrating physical components (e.g.,hardware) of a computing device 500 with which aspects of the disclosuremay be practiced. The computing device components described below may besuitable for the computing devices described above. In a basicconfiguration, the computing device 500 may include at least oneprocessing unit 502 and a system memory 504. Depending on theconfiguration and type of computing device, the system memory 504 maycomprise, but is not limited to, volatile storage (e.g., random accessmemory), non-volatile storage (e.g., read-only memory), flash memory, orany combination of such memories. The system memory 504 may include anoperating system 505 and one or more program modules 506 suitable forperforming the various aspects disclosed herein such as query executionprocessor 524 and query execution transmission processor 526. Theoperating system 505, for example, may be suitable for controlling theoperation of the computing device 500. Furthermore, embodiments of thedisclosure may be practiced in conjunction with a graphics library,other operating systems, or any other application program and is notlimited to any particular application or system. This basicconfiguration is illustrated in FIG. 5 by those components within adashed line 508. The computing device 500 may have additional featuresor functionality. For example, the computing device 500 may also includeadditional data storage devices (removable and/or non-removable) suchas, for example, magnetic disks, optical disks, or tape. Such additionalstorage is illustrated in FIG. 5 by a removable storage device 509 and anon-removable storage device 510.

As stated above, a number of program modules and data files may bestored in the system memory 504. While executing on the processing unit502, the program modules 506 (e.g., application 520) may performprocesses including, but not limited to, the aspects, as describedherein. Other program modules that may be used in accordance withaspects of the present disclosure may include electronic mail andcontacts applications, word processing applications, spreadsheetapplications, database applications, slide presentation applications,drawing or computer-aided application programs, etc.

Furthermore, embodiments of the disclosure may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. For example, embodiments of the disclosure may bepracticed via a system-on-a-chip (SOC) where each or many of thecomponents illustrated in FIG. 5 may be integrated onto a singleintegrated circuit. Such an SOC device may include one or moreprocessing units, graphics units, communications units, systemvirtualization units and various application functionality all of whichare integrated (or “burned”) onto the chip substrate as a singleintegrated circuit. When operating via an SOC, the functionality,described herein, with respect to the capability of client to switchprotocols may be operated via application-specific logic integrated withother components of the computing device 500 on the single integratedcircuit (chip). Embodiments of the disclosure may also be practicedusing other technologies capable of performing logical operations suchas, for example, AND, OR, and NOT, including but not limited tomechanical, optical, fluidic, and quantum technologies. In addition,embodiments of the disclosure may be practiced within a general purposecomputer or in any other circuits or systems.

The computing device 500 may also have one or more input device(s) 512such as a keyboard, a mouse, a pen, a sound or voice input device, atouch or swipe input device, etc. The output device(s) 514 such as adisplay, speakers, a printer, etc. may also be included. Theaforementioned devices are examples and others may be used. Thecomputing device 500 may include one or more communication connections516 allowing communications with other computing devices 550. Examplesof suitable communication connections 516 include, but are not limitedto, radio frequency (RF) transmitter, receiver, and/or transceivercircuitry; universal serial bus (USB), parallel, and/or serial ports.

The term computer readable media as used herein may include computerstorage media. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, or program modules. The system memory504, the removable storage device 509, and the non-removable storagedevice 510 are all computer storage media examples (e.g., memorystorage). Computer storage media may include RAM, ROM, electricallyerasable read-only memory (EEPROM), flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other article of manufacturewhich can be used to store information and which can be accessed by thecomputing device 500. Any such computer storage media may be part of thecomputing device 500. Computer storage media does not include a carrierwave or other propagated or modulated data signal.

Communication media may be embodied by computer readable instructions,data structures, program modules, or other data in a modulated datasignal, such as a carrier wave or other transport mechanism, andincludes any information delivery media. The term “modulated datasignal” may describe a signal that has one or more characteristics setor changed in such a manner as to encode information in the signal. Byway of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), infrared, andother wireless media.

FIGS. 6A and 6B illustrate a mobile computing device 600, for example, amobile telephone, a smart phone, wearable computer (such as a smartwatch), a tablet computer, a laptop computer, and the like, with whichembodiments of the disclosure may be practiced. In some aspects, theclient may be a mobile computing device. With reference to FIG. 6A, oneaspect of a mobile computing device 600 for implementing the aspects isillustrated. In a basic configuration, the mobile computing device 600is a handheld computer having both input elements and output elements.The mobile computing device 600 typically includes a display 605 and oneor more input buttons 610 that allow the user to enter information intothe mobile computing device 600. The display 605 of the mobile computingdevice 600 may also function as an input device (e.g., a touch screendisplay). If included, an optional side input element 615 allows furtheruser input. The side input element 615 may be a rotary switch, a button,or any other type of manual input element. In alternative aspects,mobile computing device 600 may incorporate more or less input elements.For example, the display 605 may not be a touch screen in someembodiments. In yet another alternative embodiment, the mobile computingdevice 600 is a portable phone system, such as a cellular phone. Themobile computing device 600 may also include an optional keypad 635.Optional keypad 635 may be a physical keypad or a “soft” keypadgenerated on the touch screen display. In various embodiments, theoutput elements include the display 605 for showing a graphical userinterface (GUI), a visual indicator 620 (e.g., a light emitting diode),and/or an audio transducer 625 (e.g., a speaker). In some aspects, themobile computing device 600 incorporates a vibration transducer forproviding the user with tactile feedback. In yet another aspect, themobile computing device 600 incorporates input and/or output ports, suchas an audio input (e.g., a microphone jack), an audio output (e.g., aheadphone jack), and a video output (e.g., a HDMI port) for sendingsignals to or receiving signals from an external device.

FIG. 6B is a block diagram illustrating the architecture of one aspectof a mobile computing device. That is, the mobile computing device 600can incorporate a system (e.g., an architecture) 602 to implement someaspects. In one embodiment, the system 602 is implemented as a “smartphone” capable of running one or more applications (e.g., browser,e-mail, calendaring, contact managers, messaging clients, games, andmedia clients/players). In some aspects, the system 602 is integrated asa computing device, such as an integrated personal digital assistant(PDA) and wireless phone.

One or more application programs 666 may be loaded into the memory 662and run on or in association with the operating system 664. Examples ofthe application programs include phone dialer programs, e-mail programs,personal information management (PIM) programs, word processingprograms, spreadsheet programs, Internet browser programs, messagingprograms, and so forth. The system 602 also includes a non-volatilestorage area 668 within the memory 662. The non-volatile storage area668 may be used to store persistent information that should not be lostif the system 602 is powered down. The application programs 666 may useand store information in the non-volatile storage area 668, such ase-mail or other messages used by an e-mail application, and the like. Asynchronization application (not shown) also resides on the system 602and is programmed to interact with a corresponding synchronizationapplication resident on a host computer to keep the information storedin the non-volatile storage area 668 synchronized with correspondinginformation stored at the host computer. As should be appreciated, otherapplications may be loaded into the memory 662 and run on the mobilecomputing device 600 described herein (e.g., search engine, extractormodule, relevancy ranking module, answer scoring module, etc.).

The system 602 has a power supply 670, which may be implemented as oneor more batteries. The power supply 670 might further include anexternal power source, such as an AC adapter or a powered docking cradlethat supplements or recharges the batteries.

The system 602 may also include a radio interface layer 672 thatperforms the function of transmitting and receiving radio frequencycommunications. The radio interface layer 672 facilitates wirelessconnectivity between the system 602 and the “outside world,” via acommunications carrier or service provider. Transmissions to and fromthe radio interface layer 672 are conducted under control of theoperating system 664. In other words, communications received by theradio interface layer 672 may be disseminated to the applicationprograms 666 via the operating system 664, and vice versa.

The visual indicator 620 may be used to provide visual notifications,and/or an audio interface 674 may be used for producing audiblenotifications via the audio transducer 625. In the illustratedembodiment, the visual indicator 620 is a light emitting diode (LED) andthe audio transducer 625 is a speaker. These devices may be directlycoupled to the power supply 670 so that when activated, they remain onfor a duration dictated by the notification mechanism even though theprocessor 660 and other components might shut down for conservingbattery power. The LED may be programmed to remain on indefinitely untilthe user takes action to indicate the powered-on status of the device.The audio interface 674 is used to provide audible signals to andreceive audible signals from the user. For example, in addition to beingcoupled to the audio transducer 625, the audio interface 674 may also becoupled to a microphone to receive audible input, such as to facilitatea telephone conversation. In accordance with embodiments of the presentdisclosure, the microphone may also serve as an audio sensor tofacilitate control of notifications, as will be described below. Thesystem 602 may further include a video interface 676 that enables anoperation of an on-board camera 630 to record still images, videostream, and the like.

A mobile computing device 600 implementing the system 602 may haveadditional features or functionality. For example, the mobile computingdevice 600 may also include additional data storage devices (removableand/or non-removable) such as, magnetic disks, optical disks, or tape.Such additional storage is illustrated in FIG. 6B by the non-volatilestorage area 668.

Data/information generated or captured by the mobile computing device600 and stored via the system 602 may be stored locally on the mobilecomputing device 600, as described above, or the data may be stored onany number of storage media that may be accessed by the device via theradio interface layer 672 or via a wired connection between the mobilecomputing device 600 and a separate computing device associated with themobile computing device 600, for example, a server computer in adistributed computing network, such as the Internet. As should beappreciated such data/information may be accessed via the mobilecomputing device 600 via the radio interface layer 672 or via adistributed computing network. Similarly, such data/information may bereadily transferred between computing devices for storage and useaccording to well-known data/information transfer and storage means,including electronic mail and collaborative data/information sharingsystems.

FIG. 7 illustrates one aspect of the architecture of a system forprocessing data received at a computing system from a remote source,such as a personal computer 704, tablet computing device 706, or mobilecomputing device 708, as described above. Content displayed at serverdevice 702 may be stored in different communication channels or otherstorage types. For example, various documents may be stored using adirectory service 722, a web portal 724, a mailbox service 726, aninstant messaging store 728, or a social networking site 730. Querycompilation processor 721 may be employed by a client that communicateswith server device 702, and/or query execution transmission processor720 may be employed by server device 702. The server device 702 mayprovide data to and from a client computing device such as a personalcomputer 704, a tablet computing device 706 and/or a mobile computingdevice 708 (e.g., a smart phone) through a network 715. By way ofexample, the computer system described above may be embodied in apersonal computer 704, a tablet computing device 706 and/or a mobilecomputing device 708 (e.g., a smart phone). Any of these embodiments ofthe computing devices may obtain content from the store 716, in additionto receiving graphical data useable to be either pre-processed at agraphic-originating system, or post-processed at a receiving computingsystem.

FIG. 8 illustrates an exemplary tablet computing device 800 that mayexecute one or more aspects disclosed herein. In addition, the aspectsand functionalities described herein may operate over distributedsystems (e.g., cloud-based computing systems), where applicationfunctionality, memory, data storage and retrieval and various processingfunctions may be operated remotely from each other over a distributedcomputing network, such as the Internet or an intranet. User interfacesand information of various types may be displayed via on-board computingdevice displays or via remote display units associated with one or morecomputing devices. For example user interfaces and information ofvarious types may be displayed and interacted with on a wall surfaceonto which user interfaces and information of various types areprojected. Interaction with the multitude of computing systems withwhich embodiments of the invention may be practiced include, keystrokeentry, touch screen entry, voice or other audio entry, gesture entrywhere an associated computing device is equipped with detection (e.g.,camera) functionality for capturing and interpreting user gestures forcontrolling the functionality of the computing device, and the like.

As will be understood from the foregoing disclosure, one aspect of thetechnology relates to a system comprising: at least one processor; and amemory storing instructions that when executed by the at least oneprocessor perform a set of operations. The operations comprise:receiving a query for information stored in a graph, wherein the graphcomprises a plurality of graph subparts; executing the query in a graphsubpart of the plurality of graph subparts to generate an intermediateresult and identify one or more cross-graph reference resourcesassociated with one or more other graph subparts of the graph;generating, based on the one or more cross-graph reference resources, aquery execution context associated with the query for informationcomprising at least a part of the intermediate result and at least apart of the query; and providing, to at least one of the one or moreother graph subparts of the graph, the query execution context forcontinued execution of the query for information in the at least one ofthe one or more other graph subparts. In an example, executing the queryin the subpart of the plurality of subparts comprises: identifying,based on the query for information, the graph subpart from the pluralityof graph subparts based on determining a parameter of the query forinformation is present in the graph subpart. In another example,generating the query execution context and providing the query executioncontext is performed based on a determination that the intermediateresult comprises the one or more cross-graph reference resources. In afurther example, the intermediate result comprises one or more partialmatches for the query, wherein a partial match comprises informationidentified in the graph subpart and stored in at least one of the one ormore other graph subparts. In yet another example, the set of operationsfurther comprises: generating a compiled query for the received query,wherein the compiled query is executable in a virtual machine. In afurther still example, the query execution context comprises a securitycontext indicating access control information for information in thegraph. In another example, the intermediate result comprises the one ormore cross-graph reference resources.

In another aspect, the technology relates to a computer-implementedmethod for executing a query for information in a graph subpart of agraph. The method comprises: receiving the query for information in thegraph subpart; traversing the graph subpart to generate a traversal pathassociated with the query for information, wherein the traversal path iscomprised of one or more resources and one or more relationships;determining whether a resource of the traversal path is a cross-graphreference resource associated with a subsequent graph subpart of thegraph; based on determining that the resource of the traversal path is across-graph reference resource, storing the traversal path in atraversal path data structure for transmission to the subsequent graphsubpart; and based on determining that the resource of the traversalpath is not a cross-graph reference resource, providing the traversalpath as a result to the query for information. In an example, query forinformation comprises execution context information, and whereintraversing the graph subpart comprises evaluating the graph subpart fromone or more resources identified in the execution context information.In another example, the execution context information comprises thetraversal path data structure. In a further example, the query forinformation is received from another graph subpart. In yet anotherexample, the method further comprises generating a compiled query forthe received query, wherein the compiled query is executable in avirtual machine. In a further still example, the execution contextcomprises a security context indicating access control information forinformation in the graph.

In a further aspect, the technology relates to anothercomputer-implemented method for executing a query for information acrossa plurality of graph subparts of a graph. The method comprises:receiving the query for information stored in the graph; identifying agraph subpart from the plurality of graph subparts; traversing the graphsubpart to generate a traversal path associated with the query forinformation, wherein the traversal path is comprised of one or moreresources and one or more relationships; determining whether a resourceof the traversal path is a cross-graph reference resource associatedwith a subsequent graph subpart of the graph; based on determining thatthe resource of the traversal path is a cross-graph reference resource,generating a query execution context associated with the query forinformation comprising at least a part of the traversal path and atleast a part of the query; and providing, to the subsequent graphsubpart, the query execution context for continued execution of thequery for information in the subsequent graph subpart. In an example,the query for information comprises execution context information, andwherein traversing the graph subpart comprises evaluating the graphsubpart from one or more resources identified in the execution contextinformation. In another example, the method further comprises: based ondetermining that the resource of the traversal path is not a cross-graphreference resource, providing the traversal path as a result to thequery for information. In a further example, identifying the graphsubpart comprises identifying the graph subpart based on determining aparameter of the query for information is present in the graph subpartfrom the plurality of graph subparts. In yet another example, the methodfurther comprises generating a compiled query for the received query,wherein the compiled query is executable in a virtual machine. In afurther still example, the query execution context comprises a securitycontext indicating access control information for information in thegraph. In another example, the query for information is received fromanother graph subpart of the graph.

Aspects of the present disclosure, for example, are described above withreference to block diagrams and/or operational illustrations of methods,systems, and computer program products according to aspects of thedisclosure. The functions/acts noted in the blocks may occur out of theorder as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

The description and illustration of one or more aspects provided in thisapplication are not intended to limit or restrict the scope of thedisclosure as claimed in any way. The aspects, examples, and detailsprovided in this application are considered sufficient to conveypossession and enable others to make and use the best mode of claimeddisclosure. The claimed disclosure should not be construed as beinglimited to any aspect, example, or detail provided in this application.Regardless of whether shown and described in combination or separately,the various features (both structural and methodological) are intendedto be selectively included or omitted to produce an embodiment with aparticular set of features. Having been provided with the descriptionand illustration of the present application, one skilled in the art mayenvision variations, modifications, and alternate aspects falling withinthe spirit of the broader aspects of the general inventive conceptembodied in this application that do not depart from the broader scopeof the claimed disclosure.

What is claimed is:
 1. A system comprising: at least one processor; anda memory storing instructions that when executed by the at least oneprocessor perform a set of operations comprising: receiving a query forinformation stored in a graph, wherein the graph is stored as aplurality of graph subparts; executing the query in a first graphsubpart of the plurality of graph subparts to generate an intermediateresult associated with the first graph subpart, wherein the intermediateresult comprises a cross-graph reference resource of the first graphsubpart that indicates a second graph subpart of the plurality of graphsubparts, wherein the cross-graph reference resource comprises at leastone of: a resource identifier of one or more resources in the secondgraph subpart, a query used to identify the one or more resources in thesecond graph subpart, a subpart identifier for the second graph subpart,or one or more properties associated with the one or more resources inthe second graph subpart; generating, based on the cross-graph referenceresource, a query execution context associated with the query forinformation comprising at least a part of the intermediate result fromthe first graph subpart and at least a part of the query; and providing,to the second graph subpart indicated by the cross-graph referenceresource, the query execution context to continue execution of the queryfor information in the second graph subpart indicated by the cross-graphreference resource.
 2. The system of claim 1, wherein executing thequery in the first graph subpart of the plurality of graph subpartscomprises: identifying, based on the query for information, the firstgraph subpart from the plurality of graph subparts based on determininga parameter of the query for information is present in the first graphsubpart.
 3. The system of claim 1, wherein generating the queryexecution context and providing the query execution context is performedbased on a determination that the intermediate result comprises thecross-graph reference resource.
 4. The system of claim 1, wherein theintermediate result comprises one or more partial matches for the query,wherein a partial match comprises information identified in the firstgraph subpart and stored in the second graph subpart.
 5. The system ofclaim 1, wherein the set of operations further comprises: generating acompiled query for the received query, wherein the compiled query isexecutable in a virtual machine.
 6. The system of claim 1, wherein thequery execution context comprises a security context indicating accesscontrol information for information in the graph.
 7. The system of claim1, wherein the first graph subpart is stored by the system and whereinthe second graph subpart is stored by another system.
 8. Acomputer-implemented method for executing a query for information in afirst graph subpart of a graph that is stored as a plurality of graphsubparts, the method comprising: receiving the query for information inthe first graph subpart; traversing the graph subpart to generate atraversal path associated with the query for information, wherein thetraversal path is comprised of one or more resources and one or morerelationships; determining that the traversal path is a cross-graphreference resource of the first graph subpart that indicates a secondgraph subpart of the plurality of graph subparts; based on determiningthat the traversal path includes a cross-graph reference resource,storing the traversal path in a traversal path data structure fortransmission to the second graph subpart indicated by the cross-graphreference resource, wherein the cross-graph reference resource comprisesat least one of: a resource identifier of one or more resources in thesecond graph subpart, a query used to identify the one or more resourcesin the second graph subpart, a subpart identifier for the second graphsubpart, or one or more properties associated with the one or moreresources in the second graph subpart; and transmitting the traversalpath data structure to the second graph subpart indicated by thecross-graph reference resource.
 9. The computer-implemented method ofclaim 8, wherein query for information comprises execution contextinformation, and wherein traversing the first graph subpart comprisesevaluating the first graph subpart from one or more resources identifiedin the execution context information.
 10. The computer-implementedmethod of claim 9, wherein the execution context information comprisesthe traversal path data structure.
 11. The computer-implemented methodof claim 8, wherein the query for information is received from a thirdgraph subpart of the plurality of graph subparts.
 12. Thecomputer-implemented method of claim 8, further comprising generating acompiled query for the received query, wherein the compiled query isexecutable in a virtual machine.
 13. The computer-implemented method ofclaim 9, wherein the execution context information comprises a securitycontext indicating access control information for information in thegraph.
 14. A computer-implemented method for executing a query forinformation across a plurality of graph subparts of a graph, the methodcomprising: receiving the query for information stored in the graph;identifying a graph subpart from the plurality of graph subparts;traversing the first graph subpart to generate a traversal pathassociated with the query for information, wherein the traversal path iscomprised of one or more resources and one or more relationships;determining whether a resource of the traversal path is a cross-graphreference resource of the first graph subpart that indicates a secondgraph subpart of the plurality of graph subparts; based on determiningthat the resource of the traversal path is a cross-graph referenceresource, generating a query execution context associated with the queryfor information comprising at least a part of the traversal path and atleast a part of the query, wherein the cross-graph reference resourcecomprises at least one of: a resource identifier of one or moreresources in the second graph subpart, a query used to identify the oneor more resources in the second graph subpart, a subpart identifier forthe second graph subpart, or one or more properties associated with theone or more resources in the second graph subpart; and providing, to thesecond graph subpart indicated by the cross-graph reference resource,the query execution context to continue execution of the query forinformation in the second graph subpart of the plurality of graphsubparts indicated by the cross-graph reference resource.
 15. Thecomputer-implemented method of claim 14, wherein the query forinformation comprises execution context information, and whereintraversing the first graph subpart comprises evaluating the first graphsubpart from one or more resources identified in the execution contextinformation.
 16. The computer-implemented method of claim 14, whereinthe first graph subpart is identified based on determining a parameterof the query for information is present in the first graph subpart fromthe plurality of graph subparts.
 17. The computer-implemented method ofclaim 14, further comprising generating a compiled query for thereceived query, wherein the compiled query is executable in a virtualmachine.
 18. The computer-implemented method of claim 14, wherein thequery execution context comprises a security context indicating accesscontrol information for information in the graph.
 19. Thecomputer-implemented method of claim 14, wherein the query forinformation is received from a third graph subpart of the plurality ofgraph subparts.
 20. The computer-implemented method of claim 14,wherein: the first graph subpart is stored by a first computing device;the second graph subpart is stored by a second computing device; and thequery execution context to continue execution of the query forinformation in the second graph subpart is provided, by the firstcomputing device, to the second computing device.